Skip to content

Introduce EEPROM support (#166) #167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

jgfoster
Copy link
Member

@jgfoster jgfoster commented Oct 3, 2020

First, is this really as easy as it seems? I copied EEPROM.h from here, and added lines 30-35. It seems to compile and one function gives the expected value (obviously more testing needs to be done; see below).

Is it possible to create a branch and merge this into the branch (unless you think it is okay in master)? I'd like to invite someone to add more tests and would prefer that they contribute here rather than through my fork (but that is a fine second-best alternative).

@ianfixes
Copy link
Collaborator

ianfixes commented Oct 5, 2020

I wouldn't be surprised if this is how easy it was, it looks like EEPROM just provides an alternate storage mechanism. I would defer to @per1234 on whether there are compiler directives that should block this code from being included on certain platforms.

Also, I'd prefer to add unit tests of (at least some) read, write, and comparison functions just to prove that the implementation -- obvious though it is -- matches what is expected.

@jgfoster
Copy link
Member Author

jgfoster commented Oct 5, 2020

I agree that more tests are needed, but that is what students are for! I can have them contribute the additional tests to my private repository or to a branch here. I thought that a branch here would be more realistic. So would it be appropriate to have a branch that doesn't have adequate testing yet, and then once the branch is up to par it could be merged into master?

@ianfixes
Copy link
Collaborator

ianfixes commented Oct 5, 2020

Absolutely, in CONTRIBUTING.md I describe using a branch called tdd for that purpose.

@jgfoster
Copy link
Member Author

jgfoster commented Oct 5, 2020

Thanks. I see now how to submit a PR to a branch. I'll do that...

@jgfoster jgfoster closed this Oct 5, 2020
@ianfixes
Copy link
Collaborator

ianfixes commented Oct 5, 2020

Just for git's issue-linking visibility, this was to address #166

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants